Ensure we always startup with a rustls
CryptoProvider
(main)
#601
+23
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #595. (for now)
The
rustls
library recently introduced this weird behavior where they expect users to, apart from configuring the respective feature, also explictly callCryptoProvider::install_default
. Otherwise they'd simply panic at runtime whenever the first network call requiring TLS would be made. While we already made a change upstream atrust-electrum-client
, we also make sure here that we definitely, always, absolutley are sure that we have aCryptoProvider
set on startup.